Dear list,
I have the following sample:
\showframe
\setuppapersize[A8]
\setuptyping
[align={right,broad},
strip=yes,
lines=yes,
blank=halfline]
\starttext
\startXML
content content content content
content content
content content
Hi Pablo,
The example you gave in your first message about the Scite module, that is:
\usemodule[scite]
\starttext
\startXML ñ\stopXML
\stoptext
gives an error on my machine (MacOS 11.6.5 and Context version 2022.05.11
11:36), with Context saying: « The file ended when scanning
Dear list,
I have this minimal sample (with current latest from 2022.05.11 11:36 on
Linux64):
\usemodule[scite]
\starttext
\startXML ñ\stopXML
\stoptext
Commenting out the first line avoids compilation error.
Replacing ñ with n also allows compilation.
I think there may be an error
driguez
> Betreff: Re: [NTG-context] \startXML vs \startPARSEDXML
>
> On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> > Hi everyone,
> >
> > the wikipage on \starttyping
> > (https://wiki.contextgarden.net/Command/_starttyping
> > <https://wiki.cont
On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> Hi everyone,
>
> the wikipage on \starttyping
> (https://wiki.contextgarden.net/Command/_starttyping
> <https://wiki.contextgarden.net/Command/_starttyping>) says there are
> some dedicated commands, e.g. \startXML and
Hi everyone,
the wikipage on \starttyping
(https://wiki.contextgarden.net/Command/_starttyping) says there are some
dedicated commands, e.g. \startXML and \startPARSEDXML. How do they differ?
Best,
Denis
On 5/19/2019 7:38 PM, Pablo Rodriguez wrote:
Hi Hans,
I’m afraid I found another issue with UTF8 chars in attribute values
when printing them.
\starttext
\startTEXpage[offset=1em]
\startXML
\stopXML
\stopTEXpage
\stoptext
Inspecting buff-imp-xml.lua, I
Hi Hans,
I’m afraid I found another issue with UTF8 chars in attribute values
when printing them.
\starttext
\startTEXpage[offset=1em]
\startXML
\stopXML
\stopTEXpage
\stoptext
Inspecting buff-imp-xml.lua, I understand that "alsoname" should be
added to &q
e:
To limit the smaller font to \starttyping it should be
\setuptyping [typing] [style=\ttxx]
or
\setuptyping [typing] [style=smalltype]
because \starttyping is a generated command like \startXML.
Wolfgang
Taco Hoekwater schrieb am 10.09.18 um 11:32:
Hi Hans,
Repl
To limit the smaller font to \starttyping it should be
\setuptyping [typing] [style=\ttxx]
or
\setuptyping [typing] [style=smalltype]
because \starttyping is a generated command like \startXML.
Wolfgang
Taco Hoekwater schrieb am 10.09.18 um 11:32:
Hi Hans,
Replace your two
I want to differentiate the typing of XML-code with \startXML and other text with \starttyping.That doesn’t work as I expect or I misinterpret something.The minimal example shows that in the following code there is no difference between using \startXML or \starttyping
typingsetup.pdf
Description
comment: \inlineTEX{ag%befe}
\Lua\ inline comment: \inlineLUA{agb --efe}
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
> On 22 Dec 2017, at 4
\context{ag%befe}
>
> \Lua\ inline comment: \lua{agb --efe}
>
> \startTEX
> This is text. % a comment, not \comment
> \stopTEX
>
> \startXML
> This is text.
> \stopXML
>
> \startLUA
> if code=="code" then
}
\Lua\ inline comment: \lua{agb --efe}
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
Would it b
, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
Would it be possible that all comments in type and typing (at least, for
Lua, XML and TeX) would have the same formatting for
}
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
Would it be possible that all comments in type and typing (at least, fo
Hans,
[I have reported this before the meeting, but it was wiser to wait after
the meeting was over.]
I have the following sample:
%~ \usemodule[scite]
\starttext
\startTEXpage[offset=2em]
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
[offset=1em]
\startTEX
This is text. % and this is a comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
--[[
this is a
multiline comment
--]]
---[[
this isn’t a
multili
Hans,
I have the following sample:
\starttext
\startTEXpage[offset=1em]
\startTEX
This is text. % and this is a comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
--[[
and this is a
}
\startluacode
function xml.functions.processXML(t)
buffers.assign("MyXml", "\\startXML\n" .. tostring(xml.text(t)) ..
"\n\\stopXML")
context.getbuffer { "MyXml" }
end
\stopluacode
\startxmlsetups xml:a
\xmlflush{#1}
\st
Hans,
many thanks for having added \xmlprettyprinttext to ConTeXt.
I have now another problem with inline code:
\definetype[TeX][option=TEX, lines=hyphenated]
\starttext
\startTEXpage[offset=1em]
This is inline code: \TeX{\command[option=value]{final text}}
\startXML
Inline code: \TeX[option
interline space
\hrule
\startXML
tag/tag
\stopXML
\hrule
\medskip
\setuptyping[before=,after=] % - works as expected
\hrule
\starttyping
\TeX
\stoptyping
\hrule
\stoptext
Thank you for any advice!
Christoph
___
If your
,
backgroundscreen=.9]},
after={\stopframedtext}]
\definepalet[MYcolors]
[prettyone=paleblue,
prettytwo=palecyan,
prettythree=palered,
prettyfour=darkgreen]
\definepalet[XMLcolorpretty][MYcolors]
\starttext
\startXML
main type=importanthello
\setupstartstop[XmlSnippetName][color=magenta,style=\bfa]
\starttext
\startXML
main type=importanthello world/main
\stopXML
\stoptext
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat
Christopher Creutzig wrote:
\starttext
\startXML
aa::b/a
\stopXML
\stoptext
The problem is the \setpretty`\:=10 in \XMLsetspecials in
verb-xml.tex. This should only be done inside
Suggested patch (I hope it survives being sent by mail):
--- verb-xml.tex.orig 2007-07-11 11:08
Salvete,
trying to typeset an unchanged old file with a more recent ConTeXt
version, I keep running into problems. I have reduced the first of these
(others may or may not be symptoms of the same, I'll see that later) to
this input:
\starttext
\startXML
aa::b/a
\stopXML
\stoptext
It seems
\startXML
ns:tag attribute=somevalue /
\stopXML
\stoptext
%%
You can use \setpretty`\:=17 instead, if you want the colon to be
indistinguisable from the rest of the tag.
The line I've marked 'TRICK' is needed to make sure that the original
definition of \XMLsetspecials is loaded before the new
[state=start]
\setuptyping[option=color]
\starttext
\startXML ... \stopXML
\stoptext
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
28 matches
Mail list logo